Skip to content

Workflow thread context has no current thread#2964

Draft
dplyukhin wants to merge 2 commits into
mainfrom
workflowThreadContext-has-no-currentThread
Draft

Workflow thread context has no current thread#2964
dplyukhin wants to merge 2 commits into
mainfrom
workflowThreadContext-has-no-currentThread

Conversation

@dplyukhin

Copy link
Copy Markdown
Contributor

What was changed

Remove "this should never happen" message from an event that sometimes happens: a task might exceed the potential deadlock timeout before it even gets run if it takes too long to find a thread to do the work. It's unclear how to avoid this situation, so I've updated the documentation for potential deadlock timeout to account for this.

Why?

Current documentation and error messages are misleading.

Checklist

  1. Closes WorkflowThreadContext has no currentThread in RUNNING state #2959

  2. How was this tested: Added tests to show that a tasks could potentially be locked out of the thread pool forever.

  3. Any docs updates needed? I don't think so, but potentially TMPRL1101 could be more explicit about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WorkflowThreadContext has no currentThread in RUNNING state

1 participant